Skip to content

[FEAT]: Update safhandle description - #9

Open
mbagalwa wants to merge 3 commits into
Safrochain-Org:mainfrom
mbagalwa:feat/safhandle
Open

[FEAT]: Update safhandle description#9
mbagalwa wants to merge 3 commits into
Safrochain-Org:mainfrom
mbagalwa:feat/safhandle

Conversation

@mbagalwa

@mbagalwa mbagalwa commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Update the existing SafHandle listing (apps/safhandle/) so it accurately
describes the SafHandle web dApp. The entry previously described the SDK and sat
in concept status.

  • Rewrite name, shortDescription, and description to the app's real,
    code-verified features:
    • Register a short .saf name (3–32 chars, a–z 0–9 -, one per wallet);
      transfer or release it (register_name / transfer_name / release_name).
    • Resolve name → addr_safro… address and reverse-lookup — free, read-only,
      no account or fee (get_address / resolve_name / handles).
    • Connect Keplr / Leap / Cosmostation; interactive demo + reserve dashboard;
      exact on-chain fee read from contract config.
    • Phone-number handles noted as Phase 2 (not claimed as live).
  • status: conceptbeta with a testnet statusNote
    (live on safro-testnet-1; mainnet contract pending).
  • url → live app https://handle.safrochain.com.
  • links: website (app), github (open-source SafHandle SDK), and
    docs → the SafHandle SDK on npm. (The links schema has no sdk key —
    additionalProperties: false — so the SDK link lives under docs.)
  • Add version (0.1.0), languages (en), app-focused tags, and set
    updatedAt.
  • Regenerated registry.json.

Checklist (required)

  • I ran npm ci and npm run validate locally — it passed before opening this PR.
  • I ran npm run build:registry and committed the updated registry.json in this PR.
  • New or updated app folder is apps/<slug>/ with json/app.json and img/logo.png.
  • <slug> is 2–64 chars, lowercase letters and digits only (no spaces or hyphens), and slug in JSON matches the folder name.
  • Logo is PNG, 512×512 pixels. (verified by npm run validate)
  • I have the rights to submit this listing text and logo.
  • I agree my contributions are licensed under the MIT License in this repository.

Validation output (paste if useful)

​```

safrochain-app-list@1.0.0 validate
node scripts/validate.mjs

Validation OK.
​```

Summary by CodeRabbit

  • New Features

    • Updated the SafHandle app listing with refreshed product wording, added website link, and improved docs/resource links.
    • Added English language metadata and expanded the feature highlights in the app description.
  • Updates

    • Moved the app status to beta and refreshed the status note with updated deployment/contract messaging.
    • Revised tags, version, URL, and timestamps to reflect the latest release, including updated registry metadata.

@mbagalwa mbagalwa self-assigned this Jul 9, 2026
@mbagalwa mbagalwa added the documentation Improvements or additions to documentation label Jul 9, 2026
@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Review Change Stack

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • apps/safhandle/img/logo.png is excluded by !**/*.png

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0c15037b-9302-4b66-b0ad-cdc82383646c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

This PR updates SafHandle metadata in the app manifest and registry, including naming, descriptions, beta status, links, tags, language metadata, version, and timestamps.

Changes

SafHandle App and Registry Metadata Update

Layer / File(s) Summary
App manifest identity and metadata update
apps/safhandle/json/app.json
Updated product identity, descriptions, URL, version, status, tags, links, language metadata, and updatedAt.
Registry entry sync
registry.json
Updated the SafHandle registry entry to match the revised metadata and advanced the top-level generatedAt timestamp.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly matches the main change: updating the SafHandle listing description.
Description check ✅ Passed The PR description includes a solid summary, checklist, and validation output; only the rights and MIT checklist items remain unchecked.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mbagalwa
mbagalwa requested a review from Mechack08 July 23, 2026 14:46
@mbagalwa

Copy link
Copy Markdown
Contributor Author

Hey @Mechack08
Could you take a look !

@Mechack08 Mechack08 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants